ci: add Bump Version workflow for automated release prep#331
Open
SavioBS629 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a
workflow_dispatchworkflow (Bump Version) that bumps the package version across all three version-bearing files and opens a PR titledchore: bump version to <X.Y.Z>.This automates the manual three-file version bump that must precede the Release New Version workflow (per the release flow in the contributor docs).
Files bumped by the workflow
package.jsonversionpackage-lock.jsonversion+packages[""].version(vianpm version)server.jsonpackages[0].versiononly — the top-level1.0.0schema version is left untouchedAfter the bump PR merges, trigger Release New Version to tag + publish.
Inputs
version— explicit target (e.g.1.2.23), orbump—patch/minor/majorincrement (used whenversionis blank)Safety
workflow_dispatch-only (write access required to trigger)env:— no shell interpolation of user inputpermissions:(contents: write,pull-requests: write); uses the auto-providedGITHUB_TOKENVerification
Validated end-to-end on a scratch repo mirroring this structure — produces exactly the 3-file diff shape (e.g. PR #326), with
server.json's schema version untouched.🤖 Generated with Claude Code